-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat: add kube_deployment_owner metric #2782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This issue is currently awaiting triage. If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Could you provide some use cases for this metric? |
|
cd49f71
to
3cf5221
Compare
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CatherineF-dev, nmn3m The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This PR adds a new metric
kube_deployment_owner
to track ownership information for Deployments. This is particularly useful for identifying Deployments managed by Operators or other controllers in the Kubernetes ecosystem. The metric includes information about the owner's kind, name, and whether it's a controller, making it easier to understand the ownership hierarchy in clusters.How does this change affect the cardinality of KSM: increases cardinality
This change adds one new metric with additional labels (
owner_kind
,owner_name
,owner_is_controller
) for each Deployment in the cluster.Which issue(s) this PR fixes:
Fixes #2674
The new metric provides the following information: